refactor(harness): remove the veadk agentkit harness command group#604
Merged
Conversation
Harness commands now live solely under the top-level `veadk harness` group. `veadk agentkit harness invoke` was a leftover thin HTTP client fully superseded by `veadk harness invoke` (which also accepts explicit --url/--key), and its `add` was already removed. Drop the whole group; move the shared `_harness_request` helper into cli_harness.py (its only remaining caller); delete the group's contract tests; update the runtime docs that referenced it.
zakahan
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Harness commands now live solely under the top-level
veadk harnessgroup. Theveadk agentkit harnessgroup was a leftover from the original design:veadk agentkit harness addposted to a/harness/addroute the server no longer exposes — already removed in feat(harness): deployable Harness server +veadk harnessCLI (create/add/show/deploy/invoke), with OAuth2/JWT deploy #603.veadk agentkit harness invokeis fully superseded byveadk harness invoke, which isharness.json-aware (resolves url/key by--name) and also accepts explicit--url/--key. Soveadk agentkit harness invoke --harness X --url ... --key ...==veadk harness invoke --name X --url ... --key ....Keeping
harnessunder both groups was redundant and confusing.Changes
harnessgroup,harness_invoke, andagentkit.add_command(harness)fromcli_agentkit.py(drops the now-unusedimport jsonthere)._harness_requestHTTP helper intocli_harness.py(its only remaining caller —veadk harness invoke), so there's no cross-module import.tests/cli/test_cli_agentkit_harness_contract.py).veadk agentkit harness add/invoke→veadk harness add/invoke.Verification
veadk agentkit --helpno longer listsharness;veadk harness invoke --helploads fine (helper localized).ruff+pyrightclean; full suite green (272 passed).🤖 Generated with Claude Code